A good RFC is quick and easy to fill out

• Aim for a minimum number of questions/sections to fill out
• The more people add/change a template, growing it, the less likely people will actually use it

Zero yes/no answers, or otherwise very simple 1-line answers.

• Those can be put into a checklist instead. Checklists are good!

Example minimum structure:

• Problem statement / why do we need to build something?
• Goals of the system presented in design; non-goals which are out of scope
• What success looks like, and how it can be measured
• High-level overview of solution proposal
• Details
• Alternatives considered
• Risks

Links:

• https://betterprogramming.pub/goals-and-failure-modes-for-rfcs-and-technical-design-documents-c4ee1d1da6ff

This is part of an effort to provide good #documentation to allow a team to effectively collaborate.